Agenda

1. Current SSDS Status
   1. MSE
   2. M1/M2
   3. CIMT
      1. Funded another year (June 2008)
   4. AUVCTD
   5. Post processing of all of the above
2. Documentation (WIKI migration)
3. To dos in JIRA
4. Projects involving SSDS, their status, and how SSDS contributes
   1. MOOS/MSE
      1. Post processing of profiler data
      2. Metadata and other user interfaces
         1. HOOVES and metadata editing
      3. Camera integration (data stream)
      4. Watch circle alarm
      5. Processes and procedures development (metadata is inconsistent) on MSE - operations
      6. Andrew's ACE stuff (Tom) User interface and business logic.
   2. OASIS
      1. M! Turn
      2. M2 Turn
      3. NDBC Cleanup (CIMT mooring)
      4. Ops procedures and people/tools/training (XML and turns)
   3. CIMT
      1. 2 turns
   4. AUVCTD
      1. ssdsLoads is broken
      2. HOOVES
   5. SENSORS
      1. Connect the instrument interface prototype up to SSDS on MARS (adapter or alternate ingest mechanism)
   6. Others?
      1. ROVCTD
      2. LOBO
      3. BOG
      4. do we put more in SSDS?
      5. CO2 Initiative?
      6. CN Initiative?

         ---

   7. Data Aggregation
      1. Meetings
      2. 
   8. UW to Microsoft Proposal (RCO)
      1. "We (TBD) will bring SSDS up to UW and operate". SSDS collects and then Triton (WorldWind++) visualizes it. It will tie into the .NET 3.0 Workflow Framework.
   9. UCSD Response to CI IO
      1. FIREWALLED
   10. MBARI Response to CI IO
       1. FIREWALLED
   11. CSO IO
       1. Possibly a temporary system to serve as a CI proxy.
   12. LOOKING (20 days)
       1. Jim wants to merge AOSN Data System and SSDS and then connect COOP and MoQUA to that.
       2. Federated observatory prototype include components of SSDS as repository (catalog, processing and preserving data)
   13. AOSN
       1. If Jim uses looking for merge, AOSN will use that. Dependent on LOOKING.
   14. SNMP is an activity
       1. ESB at NCSA
       2. ESB at MBARI
       3. Sending packets back and forth.
       4. To get diagram
       5. SENSORS build instrument interface and connect to ESB.
       6. SSDS is on ESB to collect and catalog data.
   15. NCSA Proposal to NSF to extend SNMP work (keeps it going)
       1. Product are offered to community (OpenSource)
   16. Nekton Research/NOAA
       1. MBARI share SSDS code
       2. Nekton will package SSDS with 2 AUVs delivered.
       3. Get Nekton engineers to be self reliant with SSDS.
       4. Would they be interested in AUV science data processing?
       5. Would need something like AUVCTD portal code to convert Nekton AUV data to XML/SSDS Data model.
       6. Conference call with them.
   17. NOAA Proposal (Francisco)
       1. 
   18. CenCOOS Related to NOAA Proposal and Data Aggregation?
   19. Dalhousie
       1. Waiting on us to deliver exportable code (they can compile and run).
       2. Preconfigured properties for building for them
       3. Tracking metadata and data for their moorings.
       4. They might provide some user interfaces for SSDS.
       5. Haven't talked to them in a while.
5. What are our goals for SSDS?
   1. Internally
   2. Externally
   3. Short Term
   4. Long Term
6. How do we transition to support and what still needs to be done?
   1. Metadata editing/management (and other UIs)
   2. Plan for the transition (written) and resources needed
   3. Move core to support or vice versa.
   4. Documentation
   5. Move to Subversion (get rid of branches)
   6. Plan and agreement for future work/development
   7. Operational interfaces (component health/statistics/log crawlers)
   8. Improve data stream monitoring system (NAGIOS a possibility)
   9. Controlled vocabularies (instrument types) overlap with MMI?
   10. Load all OASIS data.
   11. Workflow for instrument data streams.
7. How do we best open source SSDS?
   1. Current licensing website
      1. Did not formalize license yet
      2. Not utilized
   2. What is still to be done to open source?
      1. Pick a license
      2. Decide on distribution mechanism (talk to Brian and Luis)
      3. Clean up code/copyright.